Chromium beta has a dependency on llvm-chromium/candidate.[1] Currently, these are its releases in the Snap Store: ---> % snapcraft status llvm-chromium Track Arch Channel Version Revision Progress latest amd64 stable 20 22 -                  candidate 21 27 -                  beta ↑ ↑ -                  edge ↑ ↑ -          arm64 stable 20 24 -                  candidate 21 25 -                  beta ↑ ↑ -                  edge ↑ ↑ -          armhf stable 20 23 -                  candidate 21 26 -                  beta ↑ ↑ -                  edge ↑ ↑ - <--- The log of recently failed Chromium builds indicate that the Store was providing Llvm-chromium from the stable channel rather than from candidate. For example, for Armhf, the log[2][attached] contains this piece of debugging information: ---> :: + find / -name '*libclang_rt*' :: /snap/llvm-chromium/23/lib/clang/20/lib/armv7-unknown-linux-gnueabihf/libclang_rt.builtins.a <--- The path element /23/ demonstrates the snap is coming from the stable channel, contrary to specified in snapcraft.yaml. This failure was also affecting Amd64, which I wanted to unblock, so I tried   snapcraft release llvm-chromium 27 candidate , which should be a no-op as that is already the revision in the candidate channel of Amd64, but then a retry on the failed Amd64 build completed successfully. I decided to preserve the Armhf failed build as evidence of this behavior. Interestingly, the issue did not affect Arm64. [1]https://git.launchpad.net/~chromium-team/chromium-browser/+git/snap-from-source/tree/snapcraft.yaml?h=beta#n168 [2]https://launchpad.net/~chromium-team/+snap/chromium-snap-from-source-beta/+build/2759958